Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==7.3.1
->==7.6.9
==0.18.1
->==0.21.2
==24.1
->==24.2
==7.4.2
->==7.4.4
==6.0.1
->==6.0.2
Release Notes
nedbat/coveragepy (coverage)
v7.6.9
Compare Source
Tomas Uribe fixed <pull 1901_>
_ a performance problem in the XMLreport. Large code bases should produce XML reports much faster now.
.. _pull 1901:https://github.com/nedbat/coveragepy/pull/19011
.. _changes_7-6-8:
v7.6.8
Compare Source
Fix: the LCOV report code assumed that a branch line that took no branches
meant that the entire line was unexecuted. This isn't true in a few cases:
the line might always raise an exception, or might have been optimized away.
Fixes
issue 1896
_.Fix: similarly, the HTML report will now explain that a line that jumps to
none of its expected destinations must have always raised an exception.
Previously, it would say something nonsensical like, "line 4 didn't jump to
line 5 because line 4 was never true, and it didn't jump to line 7 because
line 4 was always true." This was also shown in
issue 1896
_... _issue 1896:https://github.com/nedbat/coveragepy/issues/18966
.. _changes_7-6-7:
v7.6.7
Compare Source
so it's been restored to a conditional. Sorry for the churn.
.. _changes_7-6-6:
v7.6.6
Compare Source
reported in
issue 1891
_. The assert has been removed... _issue 1891:https://github.com/nedbat/coveragepy/issues/18911
.. _changes_7-6-5:
v7.6.5
Compare Source
fix: fine-tuned the exact Python version (3.12.6) when exiting from
with
statements changed how they traced. This affected whether people saw the
fix for
issue 1880
_.fix: isolate our code more from mocking in the os module that in rare cases
can cause
bizarre behavior <pytest-cov-666_>
_.refactor: some code unreachable code paths in parser.py were changed to
asserts. If you encounter any of these, please let me know!
.. _pytest-cov-666:https://github.com/pytest-dev/pytest-cov/issues/6666
.. _changes_7-6-4:
v7.6.4
Compare Source
with
statements could cause contained branches to beincorrectly marked as missing (
issue 1880
_). This is now fixed... _issue 1880:https://github.com/nedbat/coveragepy/issues/18800
.. _changes_7-6-3:
v7.6.3
Compare Source
Fix: nested context managers could incorrectly be analyzed to flag a missing
branch on the last context manager, as described in
issue 1876
_. This isnow fixed.
Fix: the missing branch message about not exiting a module had an extra
"didn't," as described in
issue 1873
_. This is now fixed... _issue 1873:https://github.com/nedbat/coveragepy/issues/18733
.. _issue 1876https://github.com/nedbat/coveragepy/issues/187676
.. _changes_7-6-2:
v7.6.2
Compare Source
Dropped support for Python 3.8 and PyPy 3.8.
Fix: a final wildcard match/case clause assigning to a name (
case _ as value
) was incorrectly marked as a missing branch. This is now fixed,closing
issue 1860
_.Fewer things are considered branches now. Lambdas, comprehensions, and
generator expressions are no longer marked as missing branches if they don't
complete execution. Closes
issue 1852
_.Fix: the HTML report didn't properly show multi-line f-strings that end with
a backslash continuation. This is now fixed, closing
issue 1836
, thanksto
LiuYinCarl and Marco Ricci <pull 1838_>
.Fix: the LCOV report now has correct line numbers (fixing
issue 1846
) andbetter branch descriptions for BRDA records (fixing
issue 1850
). Thereare other changes to lcov also, including a new configuration option
:ref:
line_checksums <config_lcov_line_checksums>
to control whether linechecksums are included in the lcov report. The default is false. To keep
checksums set it to true. All this work is thanks to Zack Weinberg
(
pull 1849
_ andpull 1851
_).Fixed the docs for multi-line regex exclusions, closing
issue 1863
_.Fixed a potential crash in the C tracer, closing
issue 1835
, thanks toJan Kühle <pull 1843_>
... _issue 1835:https://github.com/nedbat/coveragepy/issues/18355
.. _issue 1836https://github.com/nedbat/coveragepy/issues/183636
.. _pull 183https://github.com/nedbat/coveragepy/pull/1838838
.. _pull 18https://github.com/nedbat/coveragepy/pull/18431843
.. _issue 1https://github.com/nedbat/coveragepy/issues/1846/1846
.. _pull https://github.com/nedbat/coveragepy/pull/1849l/1849
.. _issuehttps://github.com/nedbat/coveragepy/issues/1850es/1850
.. _pulhttps://github.com/nedbat/coveragepy/pull/1851ull/1851
.. _isshttps://github.com/nedbat/coveragepy/issues/1852sues/1852
.. _ishttps://github.com/nedbat/coveragepy/issues/1860ssues/1860
.. _ihttps://github.com/nedbat/coveragepy/issues/1863issues/1863
.. _changes_7-6-1:
v7.6.1
Compare Source
Fix: coverage used to fail when measuring code using :func:
runpy.run_path <python:runpy.run_path>
with a :class:Path <python:pathlib.Path>
argument.This is now fixed, thanks to
Ask Hjorth Larsen <pull 1819_>
_.Fix: backslashes preceding a multi-line backslashed string could confuse the
HTML report. This is now fixed, thanks to
LiuYinCarl <pull 1828_>
_.Now we publish wheels for Python 3.13, both regular and free-threaded.
.. _pull 1819:https://github.com/nedbat/coveragepy/pull/18199
.. _pull 1828https://github.com/nedbat/coveragepy/pull/182828
.. _changes_7-6-0:
v7.6.0
Compare Source
Exclusion patterns can now be multi-line, thanks to
Daniel Diniz <pull 1807_>
. This enables many interesting exclusion use-cases, including thoserequested in issues
118 <issue 118_>
(entire files),996 <issue 996_>
_ (multiple lines only when appearing together),1741 <issue 1741_>
_ (remainder of a function), and1803 <issue 1803_>
_(arbitrary sequence of marked lines). See the :ref:
multi_line_exclude
section of the docs for more details and examples.
The JSON report now includes per-function and per-class coverage information.
Thanks to
Daniel Diniz <pull 1809_>
_ for getting the work started. Thiscloses
issue 1793
_ andissue 1532
_.Fixed an incorrect calculation of "(no class)" lines in the HTML classes
report.
Python 3.13.0b3 is supported.
.. _issue 118:https://github.com/nedbat/coveragepy/issues/1188
.. _issue 996https://github.com/nedbat/coveragepy/issues/99696
.. _issue 153https://github.com/nedbat/coveragepy/issues/1532532
.. _issue 17https://github.com/nedbat/coveragepy/issues/17411741
.. _issue 1https://github.com/nedbat/coveragepy/issues/1793/1793
.. _issue https://github.com/nedbat/coveragepy/issues/1803s/1803
.. _pullhttps://github.com/nedbat/coveragepy/pull/1807ll/1807
.. _pulhttps://github.com/nedbat/coveragepy/pull/1809ull/1809
.. _changes_7-5-4:
v7.5.4
Compare Source
If you attempt to combine statement coverage data with branch coverage data,
coverage.py used to fail with the message "Can't combine arc data with line
data" or its reverse, "Can't combine line data with arc data." These
messages used internal terminology, making it hard for people to understand
the problem. They are now changed to mention "branch coverage data" and
"statement coverage data."
Fixed a minor branch coverage problem with wildcard match/case cases using
names or guard clauses.
Started testing on 3.13 free-threading (nogil) builds of Python. I'm not
claiming full support yet. Closes
issue 1799
_... _issue 1799:https://github.com/nedbat/coveragepy/issues/17999
.. _changes_7-5-3:
v7.5.3
Compare Source
Performance improvements for combining data files, especially when measuring
line coverage. A few different quadratic behaviors were eliminated. In one
extreme case of combining 700+ data files, the time dropped from more than
three hours to seven minutes. Thanks for Kraken Tech for funding the fix.
Performance improvements for generating HTML reports, with a side benefit of
reducing memory use, closing
issue 1791
_. Thanks to Daniel Diniz forhelping to diagnose the problem.
.. _issue 1791:https://github.com/nedbat/coveragepy/issues/17911
.. _changes_7-5-2:
v7.5.2
Compare Source
Fix: nested matches of exclude patterns could exclude too much code, as
reported in
issue 1779
_. This is now fixed.Changed: previously, coverage.py would consider a module docstring to be an
executable statement if it appeared after line 1 in the file, but not
executable if it was the first line. Now module docstrings are never counted
as executable statements. This can change coverage.py's count of the number
of statements in a file, which can slightly change the coverage percentage
reported.
In the HTML report, the filter term and "hide covered" checkbox settings are
remembered between viewings, thanks to
Daniel Diniz <pull 1776_>
_.Python 3.13.0b1 is supported.
Fix: parsing error handling is improved to ensure bizarre source files are
handled gracefully, and to unblock oss-fuzz fuzzing, thanks to
Liam DeVoe <pull 1788_>
. Closesissue 1787
... _pull 1776:https://github.com/nedbat/coveragepy/pull/17766
.. _issue 1779https://github.com/nedbat/coveragepy/issues/177979
.. _issue 178https://github.com/nedbat/coveragepy/issues/1787787
.. _pull 17https://github.com/nedbat/coveragepy/pull/17881788
.. _changes_7-5-1:
v7.5.1
Compare Source
Fix: a pragma comment on the continuation lines of a multi-line statement
now excludes the statement and its body, the same as if the pragma is
on the first line. This closes
issue 754
. The fix was contributed byDaniel Diniz <pull 1773_>
.Fix: very complex source files like
this one <resolvent_lookup_>
_ couldcause a maximum recursion error when creating an HTML report. This is now
fixed, closing
issue 1774
_.HTML report improvements:
Support files (JavaScript and CSS) referenced by the HTML report now have
hashes added to their names to ensure updated files are used instead of
stale cached copies.
Missing branch coverage explanations that said "the condition was never
false" now read "the condition was always true" because it's easier to
understand.
Column sort order is remembered better as you move between the index pages,
fixing
issue 1766
. Thanks,Daniel Diniz <pull 1768_>
... _resolvent_lookup: https://github.com/sympy/sympy/blob/130950f3e6b3f97fcc17f4599ac08f70fdd2e9d4/sympy/polys/numberfields/resolvent_lookup.py
.. _issue 754https://github.com/nedbat/coveragepy/issues/75454
.. _issue 176https://github.com/nedbat/coveragepy/issues/1766766
.. _pull 17https://github.com/nedbat/coveragepy/pull/17681768
.. _pull 1https://github.com/nedbat/coveragepy/pull/1773/1773
.. _issue https://github.com/nedbat/coveragepy/issues/1774s/1774
.. _changes_7-5-0:
v7.5.0
Compare Source
Added initial support for function and class reporting in the HTML report.
There are now three index pages which link to each other: files, functions,
and classes. Other reports don't yet have this information, but it will be
added in the future where it makes sense. Feedback gladly accepted!
Finishes
issue 780
_.Other HTML report improvements:
There is now a "hide covered" checkbox to filter out 100% files, finishing
issue 1384
_.The index page is always sorted by one of its columns, with clearer
indications of the sorting.
The "previous file" shortcut key didn't work on the index page, but now it
does, fixing
issue 1765
_.The debug output showing which configuration files were tried now shows
absolute paths to help diagnose problems where settings aren't taking effect,
and is renamed from "attempted_config_files" to the more logical
"config_files_attempted."
Python 3.13.0a6 is supported.
.. _issue 780:https://github.com/nedbat/coveragepy/issues/7800
.. _issue 1384https://github.com/nedbat/coveragepy/issues/138484
.. _issue 176https://github.com/nedbat/coveragepy/issues/1765765
.. _changes_7-4-4:
v7.4.4
Compare Source
Fix: in some cases, even with
[run] relative_files=True
, a data filecould be created with absolute path names. When combined with other relative
data files, it was random whether the absolute file names would be made
relative or not. If they weren't, then a file would be listed twice in
reports, as detailed in
issue 1752
_. This is now fixed: absolute filenames are always made relative when combining. Thanks to Bruno Rodrigues dos
Santos for support.
Fix: the last case of a match/case statement had an incorrect message if the
branch was missed. It said the pattern never matched, when actually the
branch is missed if the last case always matched.
Fix: clicking a line number in the HTML report now positions more accurately.
Fix: the
report:format
setting was defined as a boolean, but should be astring. Thanks,
Tanaydin Sirin <pull 1754_>
_. It is also now documentedon the :ref:
configuration page <config_report_format>
... _issue 1752:https://github.com/nedbat/coveragepy/issues/17522
.. _pull 1754https://github.com/nedbat/coveragepy/pull/175454
.. _changes_7-4-3:
v7.4.3
Compare Source
size during iteration." This is now fixed, closing
issue 1733
_... _issue 1733:https://github.com/nedbat/coveragepy/issues/17333
.. _changes_7-4-2:
v7.4.2
Compare Source
COVERAGE_CORE=sysmon
no longer errors on 3.11 and lower,thanks
Hugo van Kemenade <pull 1747_>
_. It now issues a warning thatsys.monitoring is not available and falls back to the default core instead.
.. _pull 1747:https://github.com/nedbat/coveragepy/pull/17477
.. _changes_7-4-1:
v7.4.1
Compare Source
Python 3.13.0a3 is supported.
Fix: the JSON report now includes an explicit format version number, closing
issue 1732
_... _issue 1732:https://github.com/nedbat/coveragepy/issues/17322
.. _changes_7-4-0:
v7.4.0
Compare Source
:mod:
sys.monitoring <python:sys.monitoring>
module by defining aCOVERAGE_CORE=sysmon
environment variable. This should be faster forline coverage, but not for branch coverage, and plugins and dynamic contexts
are not yet supported with it. I am very interested to hear how it works (or
doesn't!) for you.
.. _changes_7-3-4:
v7.3.4
Compare Source
Fix: the change for multi-line signature exclusions in 7.3.3 broke other
forms of nested clauses being excluded properly. This is now fixed, closing
issue 1713
_.Fix: in the HTML report, selecting code for copying won't select the line
numbers also. Thanks,
Robert Harris <pull 1717_>
_... _issue 1713:https://github.com/nedbat/coveragepy/issues/17133
.. _pull 1717https://github.com/nedbat/coveragepy/pull/171717
.. _changes_7-3-3:
v7.3.3
Compare Source
Fix: function definitions with multi-line signatures can now be excluded by
matching any of the lines, closing
issue 684
. Thanks,Jan Rusak, Maciej Kowalczyk and Joanna Ejzel <pull 1705_>
.Fix: XML reports could fail with a TypeError if files had numeric components
that were duplicates except for leading zeroes, like
file1.py
andfile001.py
. Fixesissue 1709
_.The
coverage annotate
command used to announce that it would be removedin a future version. Enough people got in touch to say that they use it, so
it will stay. Don't expect it to keep up with other new features though.
Added new :ref:
debug options <cmd_run_debug>
:pytest
writes the pytest test name into the debug output.dataop2
writes the full data being added to CoverageData objects... _issue 684:https://github.com/nedbat/coveragepy/issues/6844
.. _pull 1705https://github.com/nedbat/coveragepy/pull/170505
.. _issue 170https://github.com/nedbat/coveragepy/issues/1709709
.. _changes_7-3-2:
v7.3.2
Compare Source
The
coverage lcov
command ignored the[report] exclude_lines
and[report] exclude_also
settings (issue 1684
). This is now fixed,thanks
Jacqueline Lee <pull 1685_>
.Sometimes SQLite will create journal files alongside the coverage.py database
files. These are ephemeral, but could be mistakenly included when combining
data files. Now they are always ignored, fixing
issue 1605
_. Thanks toBrad Smith for suggesting fixes and providing detailed debugging.
On Python 3.12+, we now disable SQLite writing journal files, which should be
a little faster.
The new 3.12 soft keyword
type
is properly bolded in HTML reports.Removed the "fullcoverage" feature used by CPython to measure the coverage of
early-imported standard library modules. CPython
stopped using it <88054_>
_ in 2021, and it stopped working completely in Python 3.13... _issue 1605:https://github.com/nedbat/coveragepy/issues/16055
.. _issue 1684https://github.com/nedbat/coveragepy/issues/168484
.. _pull 168https://github.com/nedbat/coveragepy/pull/1685685
.. _880https://github.com/python/cpython/issues/880548054
.. _changes_7-3-1:
pypa/packaging (packaging)
v24.2
Compare Source
What's Changed
__str__
by @aryanpingle in https://github.com/pypa/packaging/pull/817>
and<
by @notatallshaw in https://github.com/pypa/packaging/pull/794Metadata.name
isn't normalized by @brettcannon in https://github.com/pypa/packaging/pull/842New Contributors
Full Changelog: pypa/packaging@24.1...24.2
pytest-dev/pytest (pytest)
v7.4.4
Compare Source
v7.4.3
: pytest 7.4.3 (2023-10-24)Compare Source
Bug Fixes
#10447: Markers are now considered in the reverse mro order to ensure base class markers are considered first -- this resolves a regression.
#11239: Fixed
:=
in asserts impacting unrelated test cases.#11439: Handled an edge case where :data:
sys.stderr
might already be closed when :ref:faulthandler
is tearing down.yaml/pyyaml (pyyaml)
v6.0.2
Compare Source
What's Changed
Full Changelog: yaml/pyyaml@6.0.1...6.0.2
Configuration
📅 Schedule: Branch creation - "after 7am and before 4pm on monday" in timezone Europe/London, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.